I guess from the players connecting to the server.
Anyway, it isn't that simple to get it done in the first place and certainly not worth the effort for a demo player (no disrespect to them, but usualy nothing good comes from that group of players).

Quote from vitaly_m :

Scawen, I think you need to point out (somewhere that everyone will see) that starting from this version, we no longer need to change wheel steering limit anymore in drivers, but should rather set it to maximum, and then set up LFS properly, so it will automatically match steering degrees for every car.

Wheel turn = same as in drivers (which should be set to maximum, 900 for G27 wheel for example)
Wheel turn compensation = 1

Because a lot of people used to have turn compensation 0 and had to change steering angle in drivers to match the car's steering, otherwise real steering wheel would turn freely past the limits.

Now the life is much simplier, but not everyone might know it

If you look at the following page: https://www.lfs.net/patch-6q, you will see this in the changelog:

Force feedback steering wheel turn limitation :

In your wheel settings use a large turn amount e.g. 900 degrees
In LFS Options - Controls set "Wheel turn" slider to match that
In LFS Options - Controls set "Wheel turn compensation" to 1.00
You should now find your wheel is correctly limited in all cars

When you type !zone when Lapper is connected to your LFS server, you will get the coordinates.
If you want to get the current node, you can type: !node

Then the first thing to do is to study the regular drift code and try to understand what's happening.
Once you have grup on that, try to build on that code.

Obvious question is, what have you got so far and where did you get stuck?

Now you say:

Quote from XDriftingKingx :

By busy, I mean like, busy maintaining the server.

In your first post of this thread you said:

Quote :

I am too busy to do it myself and just want to be able to make a server

I offered some piece of advice which is still waiting to be answered.
Sometimes I wonder why people put up these questions here anyway.

Maybe it's me, but when I think I have tried anything that's possible and finaly take my chances on getting an answer on a forum, then I am all over that forum for the days to follow to try the things that are offered to me and to answer questions that have been asked to me.
No way that I would go into hiding for so many days while I am waiting to get my question/situation answered.

There are a few things mixed up in your question.
You need to create an LFS server in the first place.
Then you need to open a port for the Insim-protocol, which will enable a program to connect to your LFS server, using the Insim-protocol.
When that is done, you need to pick the application you want (there are several applications available on this forum), set it up in a way that it can connect to your LFS server (correct portnumber, correct admin password) and then it's time to start the application.
If you done it all correctly, the application will connect your LFS server and offer you a basic set of options.
Then it's time so work out how to customise the application to your needs.

To start a host: Multiplayer -> Start new host -> Select a track -> Once track is loaded you will see this:


The yellow highlight is where you can set to Allow car reset or not.

What do you mean with "unlocked it on my main pc"?
Do you play LFS on several machines?
If so, you need to unlock it on every machine you play LFS on.

And what do you mean with "And when ever I chose a higher then the first 3..."
A server which isn't in the top 3 of the list to chose from or ... ?

After a request to add two more features to this Session lap tool, I was faced with one of the biggest tasks since I started coding within the Lapper environment.
Since Lapper doesn't have the option to sort arrays, I had to build that code myself and did so within the script (I tried to add it to the Lapper core, but failed misserably).
Once that was tackled, I was able to build a routine to find the median of a series of laptimes.

Version 1.02 has the following changes:

- Added option to display average laptimes
- Added code to be able to sort (L to H) an array with numbers
- Added laptime median

Today I finished working on V1.01 of the session laps tool.
It has the following changes:

- Added recording of sectors
- Added detection of track change
- Added automatic whipe of recordings after track change
- Added manual whipe of recordings
- First lap / sectors of first lap are no longer compared with nothing
- Removed debugcode




There's one issue remaining which needs to be solved at some point.
When using "Display sectortimes" the software needs to work out, how many lap it can display, based on the amount of sectors the track has (more sectors will make the lines per lap longer, so less laps can be displayed and vice versa)

I will update the tool on all Absolute Beginners.nl servers

Last edited by Yisc[NL], Sat 2 Jul 2016, 17:42.

Either the length of the line is too long or a part of the line isn't executed for some reason.

This afternoon I worked on version 1.01 of the Session laptime tool.
I've removed debugcode and added the option to see sector times as well.
There's still an issue to solve with detecting the number of sectors (it now depends on getting that value from the Pitboard script) and detecing a new value when the track is changed (which I suspect is a problem with the Pitboard as well).
I also need to change the code to display less number of laps, when sectortimes are used.
Need to look into those issue somewhere soon.

Quote from Gutholz :

Nice
Can you put it on AB servers? With some !command to display it like the top list.
Maybe !laptimes ?

Script has now been activated (although it needs a bit of polishing at some point) on all AB-servers.
Open the screen by typing: !seslaps

After a couple of hours (you always run into difficulties you never expected to encounter) I came up with this.
There's room for 120 laps, keeps track of your best lap in the session (displayed in green) and I've implemented your wish to compare the last lap with the previous one.

Let me know what you think about this, and if there might be anything else to add to this.

That's easy to build in Lapper.
When I'm home (in about an hour) I will put that script together.

Looking very good.
You are doing a lot of good work for Lapper lately, keep it up.

Admin notify - V1.02 (small GUI to inform people if any admins are online at that server)

Changelog:

- Fixed a bug which prevented spotting a disconnect

Change the extension of the file to .lpr and add them to addonsused.lpr to be able to use it.

You were right, the disconnect wasn't working.
Here's the updated version of the script, with the disconnect working now.

Quote from lfscruise07 :

"OnDisconnect" code does not work is not activated

All code is tested and working as intended.

Quote from lfscruise07 :

So there is one more question , updated every few minutes Can you ?
Thanks for everything

As said in my previous answer, there's no need to update it every few minutes.
When an admin connects to the server, the OnConnect event is run, which then triggers the sub event 'Admin_status' which immediately updates the buttons.
Same thing when an admin disconnects, which will trigger the OnDisconnect event and that again triggers the sub event 'Admin_status' and updates the buttons.

While thinking about your questions, I realised it was my own code you are using (which is okay as I shared it with the community).
There's no need to use a scheduled event, since the admin status is updated every time an admin connects or disconnects.
As soon as the OnConnect or OnDisconnect event is executed, it automaticly runs the sub event called "Admin_status" using this command: Admin_status( $KeyFlags );
That sub event then update the buttons accordingly to what happened, so using a scheduled event is not needed.
I've included the original code, save the file, rename it to 'admin_notify.lpr' and store it in the includes folder of Lapper.
Then make sure it's listed in the file 'addonsused.lpr'

You could try to set a 0 for seconds, instead of the *
Then it should execute at each minute.

Then you should debug the code.
Place some code in the sub-event which should display a chatmessage or a message on the console.
Then you will know if the sub-event is executed or not.
If it isn't, then there's something wrong with the scheduled action.
If it is, then there's a problem in the sub-event.

At first glance I don't see any mistakes.
Is Lapper throwing an error and if so, could you post that?